Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Selenium] Add DevWorkspaceHappyPath e2e typescript test #19152

Merged
merged 4 commits into from
Feb 25, 2021

Conversation

SkorikSergey
Copy link
Contributor

What does this PR do?

Add DevWorkspaceHappyPath typescript e2e test that will check workspaces created by devworkspace-controller.

What issues does this PR fix or reference?

#18888

@SkorikSergey SkorikSergey added status/in-progress This issue has been taken by an engineer and is under active development. kind/task Internal things, technical debt, and to-do tasks to be performed. area/qe labels Feb 25, 2021
@SkorikSergey SkorikSergey self-assigned this Feb 25, 2021
@che-bot
Copy link
Contributor

che-bot commented Feb 25, 2021

❌ E2E Happy path tests failed ❗

See Details

Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)

  • Use comment "[crw-ci-test]" to rerun happy path E2E test.
  • Use comment "[crw-ci-test --rebuild]" to re-build the images and rerun happy path E2E test.

suite('Workspace creation via factory url', async () => {

let factoryUrl : string = `${TestConstants.TS_SELENIUM_DEVWORKSPACE_URL}`;
const workspaceSampleName: string = 'web-nodejs-sample';
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Workspace name web-nodejs-sample could be misleading depending on which devworkspace devfile URL is set.

What if we name test workspace as devworkspace-sample, not linking to concrete supported language?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For now this test will check workspace created from flattened_theia-next.yaml yaml. And it uses web-nodejs-sample.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IF there is only one type of supported workspaces, I might make sense to express it in the test code, e.g.:

// This test checks only workspace created from "web-nodejs-sample" https://github.com/devfile/devworkspace-operator/blob/main/samples/flattened_theia-next.yaml.

/**
* URL of the workspace created by devworkspace-controller
*/
TS_SELENIUM_DEVWORKSPACE_URL: process.env.TS_SELENIUM_DEVWORKSPACE_URL
Copy link
Contributor

@dmytro-ndp dmytro-ndp Feb 25, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it actually existed workspace URL or URL to it's devfile ?

If it's URL to devfile which is used to create devworkspace, TS_SELENIUM_DEVWORKSPACE_DEVFILE_URL name is more relevant to value.

Copy link
Contributor Author

@SkorikSergey SkorikSergey Feb 25, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is url of existed workspace.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see. We can keep it as proof of conception, but in future there should be factory URL with link to raw devfile, as far as I know.

Co-authored-by: Radim Hopp <rhopp@redhat.com>
@che-bot
Copy link
Contributor

che-bot commented Feb 25, 2021

✅ E2E Happy path tests succeed 🎉

See Details

Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)

  • Use comment "[crw-ci-test]" to rerun happy path E2E test.
  • Use comment "[crw-ci-test --rebuild]" to re-build the images and rerun happy path E2E test.

@SkorikSergey SkorikSergey marked this pull request as ready for review February 25, 2021 15:12
@SkorikSergey SkorikSergey added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. and removed status/in-progress This issue has been taken by an engineer and is under active development. labels Feb 25, 2021
@che-bot
Copy link
Contributor

che-bot commented Feb 25, 2021

❌ E2E Happy path tests failed ❗

See Details

Tested with Eclipse Che Multiuser User on K8S (minikube v1.1.1)

  • Use comment "[crw-ci-test]" to rerun happy path E2E test.
  • Use comment "[crw-ci-test --rebuild]" to re-build the images and rerun happy path E2E test.

@SkorikSergey SkorikSergey merged commit fa8b05a into master Feb 25, 2021
@SkorikSergey SkorikSergey deleted the addDevWorkspaceHappyPath branch February 25, 2021 16:29
@che-bot che-bot removed the status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. label Feb 25, 2021
@che-bot che-bot added this to the 7.27 milestone Feb 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/qe kind/task Internal things, technical debt, and to-do tasks to be performed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants